[Experimental] Complete fix for punch ceiling stuck #727
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
And some explanations.
How punch ceiling stuck happens
How lag compensation system works
There's a lag compensation system (or lagcomp in the following) to help players register targets under network issues.
During "lagcomp section", every compensated entity is moved for a calculated offset, and eventually returned to a relatively original position.
What punch does to survivors
Besidees damages and fly, the game will try lifting survivors by 18 units so that they travel further away from the Tank.
When these two combines
Punching are lag-compensated. When a survivor gets punched, his lerped position may be possible for a 18-unit up, but not the case when "lagcomp section" finishes. Eventually he might get stuck in the ceiling.
Blame lagcomp?
Lagcomp actually provides the functionality to prevent stuck when rewinding entity positions.
But it defaults to off.
So this plugin simply turns on that functionality ONLY when a survivor gets punched, so the cost should be minumum (2 more traces at most per landed punch).